TeX 1995 July/TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO/tex-k/tex-k-archive.past/tex-k-archive.gz/tex-k-archive/000780_pete@lovelace.…ni-frankfurt.de_Fri Jul 15 11:12:54 1994.msg

Internet Message Format | 1994-10-11 | 5KB

Received: from riese.informatik.uni-frankfurt.de (riese.thi.informatik.uni-frankfurt.de) by cs.umb.edu with SMTP id AA26270
  (5.65c/IDA-1.4.4 for <[e-mail]>); Fri, 15 Jul 1994 03:12:02 -0400
Received: from lovelace.informatik.uni-frankfurt.de (lovelace.thi.informatik.uni-frankfurt.de) by riese.informatik.uni-frankfurt.de (4.1/THI-peleuck2.1)
    id AA19121; Fri, 15 Jul 94 09:12:57 +0200
Content-Transfer-Encoding: binary
Content-Type: text/plain; charset=ISO-8859-1
Received: by lovelace.informatik.uni-frankfurt.de (4.1/SMI-4.1)
    id AA14035; Fri, 15 Jul 94 09:12:54 +0200
Date: Fri, 15 Jul 94 09:12:54 +0200
From: [e-mail] (Peter Dyballa)
Message-Id: <[e-mail]>
To: [e-mail]
Subject: Re: converting to latex2e

Timo Kuronen writes:
>
> You can generate all necessary pk-files as a batch run:
>
> #!/bin/sh
> MakeTeXPK dcr5 600 600 magstep\(0.0\) qmsesz
> MakeTeXPK dcr6 600 600 magstep\(0.0\) qmsesz
> MakeTeXPK dcr7 600 600 magstep\(0.0\) qmsesz
> ...
>
> and move them to proper directory, e.g.
> /usr/local/lib/texmf/fonts/public/dc/pk/qmsesz
> or whatever. You would not need MakeTeXPK any more afterwards.
>
Making (and storing) a first set of PK files is _the_ job for Peter Damian Cugley's mff[-29]. Commanding

    mff [-v] -m0,h,1,2,... dc{r,b,sl,ti,...}{8,9,10,12,17}-

and having in the home directory a file called .mffrc with that contents:

    #  my personal mff startup file
    #  created - Damian Cugley <[e-mail]> Mon 15 Jan 1990

    #  where my font directories are:
    -z qmsesz
    -d 600
    #  bitmap files are stored in directories named after the
    #  printing engine rather than the resolution:

    -P /usr/local/tex/lib/fonts/PK/%z/dc
    -T /usr/local/tex/lib/fonts/TFM/dc
or
    -P /usr/local/lib/texmf/fonts/public/dc/pk/%z
    -T /usr/local/lib/texmf/fonts/public/dc/tfm

moves TFM and PK files to the directories named. It might take a weekend or even more to make a first set of PK (and TFM) files. If you're going to mirror the structure of input MF files on the output of TFM and PK files you might need to use a batch job that overwrites ~/.mffrc with new settings when a new metafont family is started ...


> You may also modify MakeTeXPK to select DESTDIR more carefully, like:
> case "$1" in
>     dc*) DESTDIR="/usr/local/lib/texmf/fonts/public/dc/pk";;
>     cm*) DESTDIR="/usr/local/lib/texmf/fonts/public/cm/pk";;
>   logo*) DESTDIR="/usr/local/lib/texmf/fonts/public/logo/pk";;
>       *) DESTDIR="/usr/local/lib/texmf/fonts/tmp/pk";;
> esac
> I hate this solution but I couldn't figure out anything more ingenious.
>

I augmented MakeTeXPK with such things:

at the top near the usage:
MFSUBDIR=cm
MFFACES=/usr/local/tex/lib/fonts
PATH=/usr/local/tex/bin:/usr/bin:/usr/ucb

later:
if [ -z "$LINE" ]
then
# Do we have a METAFONT source for this typeface?
    for TF in `find $MFFACES/[a-z]* -type f -follow -name "$NAME.mf" -print`
    do FACE=`expr $TF : "$MFFACES/\(.*\)/$NAME.mf"`
        break
    done
        DESTDIR=/usr/local/tex/lib/fonts/PK/$MODE/$FACE
        TFMDIR=/usr/local/tex/lib/fonts/TFM/$FACE
        PKNAME=$NAME.$DPI'pk'
        TFMNAME=$NAME.tfm

        echo mf "\mode:=$MODE; mag:=$MAG; scrollmode; input $NAME" \\\</dev/null
env MFBASES=/usr/local/tex/lib/bases MFPOOL=/usr/local/tex/lib mf "\mode:=$MODE; mag:=$MAG; scrollmode; input $NAME" </dev/null

        env TEXFONTS=. gftopk ./$GFNAME ./$PKNAME

and finally a wonderfull construction due to the fact that we have 300dpi and 600dpi printers in different departments with their own ``home directories'':

        if [ $MODE = "LaserJetIV" ]
        then
            if [ `hostname` = "python" ]
            then
                ln /usr/local/tex/lib/fonts/PK/$MODE/$FACE/$PKNAME /usr/local/tex/lib/fonts/PK/.$MODE/$PKNAME
            else
                /usr/hosts/python ln /usr/local/tex/lib/fonts/PK/$MODE/$FACE/$PKNAME /usr/local/tex/lib/fonts/PK/.$MODE/$PKNAME
            fi
        else
            if [ `hostname` = "riese" ]
            then
                ln $DESTDIR/$PKNAME /usr/local/tex/lib/fonts/PK/.$MODE/$PKNAME
            else
                /usr/hosts/riese ln $DESTDIR/$PKNAME /usr/local/tex/lib/fonts/PK/.$MODE/$PKNAME
            fi
        fi
        exit 0
else
    <job for T1FACES ... etc, i.e. PK files from PostScript fonts for xdvik>
fi

I also organised - and this might be a clue - to create directories called .CanonCX and .LaseJetIV (although HP _never_ user roman letters for their LJ 4) which contain hard links to the PK files in the PK files tree. It speeds up searching and finding the file without much cost (only tha number of hard links lets the number of blocks for inodes of the directories contents rise):

    drwxr-xr-x  2 root        86528 Jul 11 14:45 .CanonCX


Greetings

Pete

(Peter Dyballa)

Johann Wolfgang Goethe-Universit\"at        Robert-Mayer-Str. 11-15
Fachbereich 20 - Theoretische Informatik    D 60325 Frankfurt am Main
(Department for Computer Science)        (Federal Republic of Germany)

email:[e-mail]    voice/fax:[phone]/8353